An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I am trying to add testers to External Tester groups for a couple of our iOS apps and after adding them it shows "No Builds Available". This is despite the app being available to that External Tester group with other people having already installed the latest version of the app which is "Available" and not expired. Can someone please fix this? It is so frustrating the number of times I try and release apps to TestFlight and there's some issue blocking me, completely out of my control and I have to rely on someone at Apple fixing something on this terrible AppStoreConnect system.

Hello Apple Developer Support Team and Developer Community, We are seeking assistance regarding our app review status. App ID: 6758329405 Our updated version was submitted for App Review, but it has remained in “Waiting for Review” status without any progress or feedback. We have also contacted Apple through the available support channel to request assistance, but unfortunately, we have not received a response or status update so far. This has become increasingly urgent because our app is planned to support an offline bicycle exhibition and promotional event around October 1, 2026 (China’s National Day holiday). We have already completed significant preparations for the event, and the updated app is an important part of our overall launch and exhibition plan. We fully understand that Apple needs time to review every submission, and we are not asking for preferential treatment. Our main concern is that we currently have no information about the status or expected progress of the review. Could an Apple representative please help check the status of App ID 6758329405 or advise us on the appropriate way to obtain an update from the App Review team? As October 1 is approaching, any assistance or status information would be greatly appreciated. Thank you very much for your help.

Title: Guideline 5.6 and disclosed network fallback routing — how strict is "no concealment"? We received a 5.6 rejection ("features that appear to have been intentionally hidden during review") for a VPN app. After investigation, we identified that some of our servers used SNI-based domain fronting (TLS handshake to a Google hostname, real destination in the HTTP Host header) as their primary connection method in regions where our own infrastructure is blocked at the network level. We disclosed this fully in App Review Information before resubmitting: what it is, why it exists, and that we removed it from all servers. We received the same 5.6 wording again on the next submission. Questions for anyone who has navigated this: Does prior undisclosed use of a technique like this permanently flag the app/account for stricter automated review, even after the technique is removed and disclosed? Is domain fronting for VPN tunnel traffic (not just API calls) treated as inherently disqualifying under 5.6, regardless of disclosure — i.e. is there no version of "explain it" that satisfies this, only "remove it entirely"? For apps serving regions with network-level blocking of VPN protocols, is there a legitimate, App Store-safe way to maintain connectivity without triggering 5.6 — e.g. is Reality-protocol-style obfuscation treated differently from SNI fronting to a real third-party domain like Google's? Any pointers to relevant guideline clarifications or past resolved cases would help. Thanks.

Ops Chat (Apple ID 6804704354, bundle it.opsmobile.chat), iOS 1.5 build 684, was submitted for review on September 9, 2026. An expedited review was requested and granted on September 12 and again on September 15, yet the version is still "Waiting for Review" and has never entered review. This is the first public release of the messaging app of Ops Mobile, an Italian mobile operator, and our customers are waiting for it. Is there anything we can do from our side to move the review forward?

Our first iOS submission has been "In Review" for 8 days with no update, no Resolution Center message, and no request for additional information. App: Lossic Apple ID: 6806576247 Version 0.2.0, build 31 Submitted: 2026-09-06 (In Review since shortly after) Bundle is a universal record (app.lossic.Lossic). The macOS version of the same record was submitted and approved normally during this same period, so this appears to be a procedural stall on the iOS review specifically, not a content issue. I contacted the App Review team (case 102957178109) 3 days ago and have not received a reply. Could App Review please look into why the iOS review has not progressed? Happy to provide any additional information needed. Thank you.

Dear App Review Team, Our app No.IA (Apple ID: 6768742372) has been in "Waiting for Review" since July 20, 2026. This is version 3.1, resubmitted after the App Review Board cleared Guidelines 2.3.1 and 3.2.1 (Appeal Ticket APL509468). All Guideline 1.1 concerns have been addressed: metadata rewritten, in-app labels updated, screenshots replaced. We have tried: Resolution Center reply, expedited review request, phone call to Developer Support (Case 102912803305). All responses have been generic with no timeline. This app has been in review processes since May 19, 2026 — over 75 days. Any assistance would be greatly appreciated.

Hello, Thank you for your efforts to follow our guidelines. There are some outstanding issues that still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Review Environment Submission ID: 3a8aadf3-5812-4cc0-ab68-74e1f635f764 Review date: September 08, 2026 Review Device: iPad Air 11-inch (M3) Version reviewed: 1.0.2 (28) App Version Guideline 2.1(b) - Information Needed We have started the review of the app, but we are not able to continue because we cannot locate the In-App Purchases within the app at this time. Next Steps To help us proceed with the review of the app, please reply to this message providing the steps for locating the In-App Purchases in the app. Note that In-App Purchases are reviewed in an Apple-provided sandbox environment. Make sure they have been appropriately configured for review in the Apple-provided sandbox environment. If you are restricting access to In-App Purchases based on factors such as storefront or device configurations, please include this information in your reply along with steps to enable the In-App Purchases for our review. Additionally, note that the Account Holder must accept the Paid Apps Agreement in the Business section of App Store Connect before paid In-App Purchases will function. Resources Learn more about offering In-App Purchases. Learn more about testing in sandbox. Learn more about submitting In-App Purchases and subscriptions to App Review. Guideline 2.3.2 - Performance - Accurate Metadata Issue Description We noticed that your promotional image to be displayed on the App Store does not sufficiently represent the associated promoted In-App Purchase and/or win back offer. Specifically, we found the following issue with your promotional image: – Your promotional image includes text that is small or otherwise hard to read. Next Steps To resolve this issue, please revise your promotional image to ensure it is unique and accurately represents the associated promoted In-App Purchase and/or win back offer. If you have no future plans on promoting this In-App Purchase product, you can delete the associated promotional image in App Store Connect. Resources Learn how to view and edit In-App Purchase information in App Store Connect. Discover more best practices for promoting your In-App Purchases on the App Store. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Request an App Review Appointment at Meet with Apple to discuss your app's review. Appointments subject to availability during your local business hours on Tuesdays and Thursdays. Provide feedback on this message and your review experience by completing a short survey. Test on the latest betas Betas of iOS 27, iPadOS 27, macOS 27, tvOS 27 and visionOS 27 are now available. Download the latest betas to prepare your app for upcoming software releases. Learn more about installing and using Apple beta software.

Hello App Review team, We urgently need help with our iOS app (Apple ID 6810751660), which has been in Waiting for Review since September 15, 2026. This is the official app for an event that begins this evening, September 15. Thousands of attendees rely on it for schedules, results, and on-site services from the very first day. If it is not available on the App Store in the next few hours, they will not be able to use it when the event opens. We have submitted an expedited review request, and the submission will stay unchanged. Our team is standing by and will respond immediately to any question from App Review. We would be very grateful if this submission could be reviewed today. Thank you for your help.

Title: macOS app in Waiting for Review after replying to a Guideline 2.1 information request Hello, My first macOS app (App ID 6811325879, version 1.0) was submitted on 12 September 2026. On 13 September I received a Guideline 2.1 – Information Needed message regarding the limited App Review history of my account. The same day I replied in the Resolution Center with all six requested items, and I also copied the same information into the Notes field of the App Review Information section, as the message instructed. Since then the submission has been in Waiting for Review with no further messages. The app is a simple offline PDF utility: no account, no login, no in-app purchases, no network connections. Is there anything else I should provide, or is this simply normal queue time for a new developer account? Thank you.

Apple ID: [6768179663] First submitted for review: 2026-08-31 Status changed to "In Review": 2026-09-02 Current status: In Review — 14 days with no status change Submission contents: app version + 6 in-app purchase / subscription items Resolution Center: no messages from App Review App Review Status case: opened [2026-09-09], Case ID 102957220208, no reply yet Context: this is our first submission. The app includes UGC (community posts, comments, and user reporting) and AIGC, which we understand may require additional review time. Question for the App Review team: is this submission currently assigned to a reviewer and being processed, or is it sitting in the queue? And is there anything on our side — review notes, demo account access, or a specific guideline item — that we should provide in order to unblock it? We are not requesting an expedited review. Demo credentials, screenshots, or a walkthrough video can be supplied on request. Curious whether other developers are seeing similar In Review wait times this month.

Uploaded my first App for the app store! Apple said they have a very fast response time but despite their very quick response (only 8hrs after filling out all the paper work), their response felt very generic... basically saying "your a first time app creator we need more information" I responded to all questions and submitted a screen recording of the app and resubmitted for review. It's now been 4 days and no response to my resubmitted review! no email, no notice it was seen... Apple has all these stats about how fast they are to respond but if its just a quick fast initial generic response thats not really a response and its just a way for them to claim a high efficiency. Has anyone else encountered this? How long and how much back and forth should I expect publishing a basic app?

I am new and submitted an app which got reviewed twice over the last 2 weeks. I tried adding IAP in the 2nd submission but it didn't get attached. I created 3rd submission and the status says Ready for Review. The IAP says (Unable to Submit for Review To submit your items for review, add an app version for the selected platform.). There is no option to cancel the submission and restart. Previous review cycles showed "Waiting for Review" and "In Review" before I got response on reasons for rejecting the app submission. But now it appears to be stuck. I requested email support. Is there any solution that I am missing? Thanks for your help! Raja

This is a Universal App supporting iOS, macOS, iPadOS, and visionOS under a single App Record with shared in-app purchases and subscriptions. While previous iOS and visionOS submissions were approved using these shared records, today's visionOS update was rejected under Guideline 2.1 for allegedly missing visionOS-specific in-app purchase records. Unless the policy has recently changed, a separate set of records for visionOS should not be required for a Universal App. Additionally, the system only allows one screenshot per in-app purchase, making it impossible to provide separate paywall images for each platform. Two weeks and counting, the macOS In Reviews have been going into blackhole while iOS and visionOS submissions are approved in less than 24 hours.

Hello, Our app Kadoz has been in "Waiting for Review" for 8 days with no status change. Apple ID: 6807392986 Version: 1.0 (build 9) Submitted: September 6, 2026 Current status: Waiting for Review This is our first submission. App Review Information is complete, including demo account credentials for the passwordless sign-in flow. All agreements are signed and the privacy questionnaire is published. We contacted Developer Support but have not received a reply. Could you check whether anything is missing on our side? Thank you.

Hi everyone, I’m looking for guidance regarding an unusually long App Review delay. My first iOS app, EmpowerFI, has been in “Waiting for Review” for almost 30 days. In two days, it will reach a full month without moving to “In Review.” During this period, I have contacted Apple Developer Support several times. After my initial contact, Apple submitted an expedited review request as a one-time exception for my app. However, the status did not change. I contacted support again and received the following response: “We have confirmed that your app review is proceeding normally, and there is no further action you need to take.” I have followed up multiple times since then, explaining that I am not asking Apple to guarantee a review or approval date. I am simply trying to understand why this particular submission has remained in “Waiting for Review” for almost a month. Unfortunately, I continue to receive essentially the same standard response. There are no pending actions visible in App Store Connect, and Apple Support has explicitly confirmed that there is nothing further required from me. I fully understand that review times vary and that some apps may require additional scrutiny. However, almost 30 days without even moving from “Waiting for Review” to “In Review” seems exceptionally long, particularly after an expedited review request was submitted. I also know developers who submitted apps during this period and received a review response within approximately two days, so I am trying to understand whether there could be something specific affecting my submission. Has anyone recently experienced a similar delay with a first app submission? More importantly, is there any other appropriate escalation path when Developer Support confirms that everything is normal but the app remains in “Waiting for Review” for almost a month? I am not looking to bypass App Review or request guaranteed approval. I would simply like someone to investigate whether there is an issue affecting this submission or explain why it has remained in the queue for such an exceptional amount of time. Any guidance from Apple staff or developers who have experienced this recently would be greatly appreciated. Thank you,

Apple 团队及各位开发者，你们好： 我是一名独立开发者，希望就开发者会员资格终止后的沟通渠道和恢复申请流程获得指引。 我的账号下共有九款 App，其中八款此前已在 App Store 上架。近期发生的情况如下： 2026 年 9 月 11 日： App Store Connect 显示依据《Apple Developer Program 许可协议》第 3.2(f) 条发出的待终止通知，账号下此前上架的 App 被下架。 2026 年 9 月 12 日： 我通过指定的 App Review Board 表单提交申诉。该表单当时最多允许添加五款 App，提交完成页面确认已收到这五款 App 的申诉请求。 2026 年 9 月 14 日： 我陆续在这五款 App 的通讯页面收到回复。每份回复都有不同的申诉编号，但实质内容相同，均表示调查已完成，并维持终止开发者会员资格的决定。 我理解，这些回复涉及的是账户级决定，而不只是某一款 App 的普通审核拒绝。回复同时告知，会员资格正式终止后，可以申请恢复。 目前最困难的是：通知列举了可能涉及的违规行为类别，但没有指出本次认定所依据的具体事例。 例如，我仍不清楚相关认定对应的是哪款 App、哪个版本或 Build、哪项功能、哪段元数据、哪次沟通回复，或哪项账号相关活动。 我对这一结论有异议。我没有故意隐藏功能，也没有设置以规避审核为目的的机制。我愿意提供相关记录，解释可能存在的事实理解偏差，并纠正确认存在的问题。但在缺少具体事例的情况下，很难准备有针对性、可验证的说明和改进计划。 我理解开发者论坛不能代替 App Review Board 处理账户申诉。我不是要求论坛参与者直接撤销决定，也不要求披露内部检测方法、审核人员身份或第三方保密信息。 希望获得以下流程方面的指引： 申诉已有结论后，应通过哪个官方私密渠道请求具体说明？ 我已有 Developer Support 案例，希望了解如何请求足以供我核实、回应和采取改进措施的信息。 在通知没有提供具体事例的情况下，应如何组织恢复申请？ 哪些材料最有助于区分事实澄清、已经完成的改进，以及尚待实施的计划，避免依靠猜测作出不准确的陈述？ 应如何确认正式终止的生效状态，以及何时可以提交恢复申请？ 对于涉及同一账户、分别关联五款 App 的申诉编号，后续请求应如何引用和关联？ 我可以通过 Apple 官方私密支持渠道提供申诉编号、支持案例编号及相关材料，因此没有在公开帖子中列出这些信息。 这件事对我的开发工作影响很大。我希望准确理解实际问题，通过合适的程序提供有针对性的证据，并争取恢复会员资格的机会。 感谢任何关于正确渠道和后续步骤的指引。 Hello Apple team and fellow developers, I am an independent developer seeking guidance on the appropriate communication channel and process for preparing a membership reinstatement request. My account contains nine apps, eight of which had previously been available on the App Store. The timeline is as follows: September 11, 2026: App Store Connect displayed a Pending Termination Notice citing Section 3.2(f) of the Apple Developer Program License Agreement. My previously available apps were removed from the App Store. September 12, 2026: I submitted an appeal through the designated App Review Board form. The form allowed me to add a maximum of five apps at that time, and the confirmation page acknowledged receipt of the appeal request for those five apps. September 14, 2026: I received responses in the communication pages for all five apps. Each response has a different appeal ticket number, but the substantive wording is identical. The responses state that the investigation is complete and maintain the decision to terminate my developer membership. I understand that these responses concern an account-level decision, rather than an ordinary review rejection for an individual app. They also state that I may request reinstatement once the membership is formally terminated. My main difficulty is that the notifications list categories of potentially prohibited conduct without identifying a specific example underlying the finding in my case. I do not know which app, version or build, feature, metadata, communication, or account-related activity led to the decision. I disagree with the conclusion. I have not deliberately hidden functionality or implemented a mechanism intended to evade App Review. I am willing to provide relevant records, address possible factual misunderstandings, and correct any confirmed deficiencies. However, without a specific example, it is difficult to prepare a targeted, verifiable explanation and improvement plan. I understand that the Developer Forums cannot replace the App Review Board’s account appeal process. I am not asking forum participants to overturn the decision or disclose internal detection methods, reviewer identities, or third-party confidential information. I would appreciate guidance on these procedural questions: After an appeal has been decided, which official private channel should I use to request actionable clarification? I already have a Developer Support case and would like to understand how to request enough information to investigate, respond, and take appropriate corrective action. How should a reinstatement petition be organized when the notification does not identify a specific example? What evidence would best distinguish factual clarification, completed improvements, and proposed changes, without relying on speculation or making inaccurate statements? How should I confirm the effective status of formal termination and when I may submit a reinstatement request? How should I reference and associate the five app-specific appeal ticket numbers in a follow-up concerning the same membership? I can provide the appeal references, Developer Support case number, and relevant materials through an official private support channel, so I have not included those details publicly. This decision has significantly affected my development work. My goal is to understand the actual concerns, provide focused evidence through the appropriate process, and seek an opportunity to restore my membership. Thank you for any guidance on the correct channel and next steps.

I received a Pending Termination Notice under ADPLA 3.2(f) on September 1. The identical notice was posted into the message thread of every app on my account, so it's account-level rather than tied to one app. The stated evidence was repeated submissions attempting to evade review. I filed an appeal admitting the conduct rather than disputing it, and set out the remediation with dates. That was two days ago, no response yet. Since filing, I audited the rest of my apps and found competitor app names in some keyword fields. I hadn't connected that to the termination, but 3.2(f) does mention unfair competition and consumer confusion, and I had a naming complaint from another developer resolved through Apple earlier this year. My questions: Has anyone filed a second appeal while the first was still pending? I've read about a second appeal succeeding after the first missed the real cause, but mine already admits the main issue. Unsure whether adding this strengthens the case or just muddies it. Is competitor keywords the kind of thing that contributes to an account-level action, or is it normally just a 2.3.7 rejection? For anyone who has been through a 3.2(f) termination - roughly how long did the App Review Board take to respond? Happy to share how it turns out either way, since there isn't much written about this process.

Has anyone observed the intermittent issues with the AppStore Connect site? Missing app records and error banners where information should appear “Your account cannot be found” error “Please accept these terms and conditions” Could this explain why some apps remain in review or seem to wait indefinitely—perhaps due to suppressed technical bugs or errors in the site’s processing of changes, where end-to-end flows fail to complete what would otherwise yield a finished review?

My macOS app update has been sitting in "In Review" since Aug 31 at 12:50 PM PT — 13 days — with no messages, questions, or status changes in App Store Connect. ▎ App: NFS Files – NAS Drive Client ▎ App ID: 6789844265 ▎ Platform: macOS, version 2.0 (build 9) ▎ Submission ID: ac1eccf9-a982-492c-a6c4-c402c5f91d29 ▎ The identical iOS 2.0 submission, with the same review notes, was reviewed and approved on Sep 6. The earlier 4.3(a) concern on both platforms was addressed by removing the other network-file apps from my account and by the NFS-specific functionality described in the review notes. ▎ I've also submitted a request through the Contact Us form. Is the review still active, or is anything needed from me?

Hello, since July 31st, our app has been stuck in the waiting for review state for a long period of time. We have already taken some actions. July 31: first submission. August 10: after waiting for over a week, we assumed there was a problem with the review queue -> cancel and resubmit. We attempted to submit an expedited request, but there was an issue with Apple service. It keeps saying "Sorry, we didn't receive your request." August 13: request a call with the Support Team. There was a guy named Tony who answered. Unfortunately, even Apple's staff is unable to access their internal system, as he told us that, and "he don't know why"? August 14: request a call again. Apple staff - Andy took up the phone and said he could not do anything about this situation and said... We just have to wait. August 25: rejected the build, upgraded the version, and submitted once more. We're hoping that this build will get out of the stucked queue... Side notes: Attempted to submit another expedited request were unsuccessful, the problem remained, tried several times. Made an appointment for a App Review team. But even the registration is still pending. Does anyone here have suggestions or solutions for this situation? This is the first time we've encountered this situation, and it's quite strange. Isn't that a side effect of the August 8th maintenance?